X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C815B2.DF529651@onstor-exch02.onstor.net>; Tue, 23 Oct 2007 13:25:37 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Rocket98 item - bobcat to Cougar migration
Date: Tue, 23 Oct 2007 13:25:36 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E062AD0E3@onstor-exch02.onstor.net>
In-Reply-To: <471E11A3.1020805@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Rocket98 item - bobcat to Cougar migration
Thread-Index: AcgViH9AYq4P+/ORRtyJo79Q28yObwAKLAgw
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Narain Ramadass" <narain.ramadass@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>

4. The FTI code is going to need to be smart about recognizing if the
secondary flash is a linux flash or a BSD flash and act accordingly.
I don't think that you will have to reboot to perform the cluster DB
upgrade. Since the daemons are not yet running at the time FTI is
running,
you should be able to just replace the cluster DB with the one from
the secondary flash. The actual upgrade will be done when the cluster
daemons are started.=20

5. You shouldn't have to reboot after running FTI. Linux is much better
about being able to restart the appropriate init.d scripts to get
configuration changes to take effect. This needs to be worked out as
part of porting the FTI work to linux. Who is responsible for this?

7. The handling of the first 7 files is not as easy as you imply.
Many of these files simply do not exist in linux. All of the=20
network config is done in /etc/network/interfaces which does
not exist on BSD. On linux we use a shadow password file.
This requires that you convert the bsd password file into
both a passwd and shadow file. My recommendation is to first
finish the porting of the FTI code to linux before trying to
design the migration code. What you learn from the FTI porting
will enable you to succeed with the migration project.

We are not planning on changing cluster DB format so there really
won't be much to do here beyond what we already support.

We will need customers to be at some minimum level of OS release.
Probably running 3.0 is adequate. We may want to only support upgrade=20
from BSD flashes utilizing the new layout. This needs to be decided.

We are planning on changing the system upgrade procedure and
implementation
but we have not yet started on this work. Be aware of this.

-----Original Message-----
From: Narain Ramadass=20
Sent: Tuesday, October 23, 2007 8:22 AM
To: dl-Design Review
Subject: Rocket98 item - bobcat to Cougar migration

All,

Please find attached a document detailing our understanding of the=20
above-mentioned item in the Rocket98 plan.

Comments (particularly additions to the scope, modifications to the=20
workflow) would be greatly appreciated.

Thanx,
Narain.

